Fix/sort initially fetched txes - LW-12194 #1579
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rhyslbw
previously approved these changes
Jan 31, 2025
initially fetched trasactions were returned in asc order, but sliced from array start when we actually want the latest txes
mirceahasegan
dismissed stale reviews from AngelCastilloB and rhyslbw
via
72d81c0
mirceahasegan
force-pushed
the
fix/sort-initially-fetched-txes
branch
from
e4fe70b to
72d81c0
Compare
mirceahasegan
commented
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
initially fetched trasactions were returned in asc order, but sliced from array start when we actually want the latest txes
Proposed Solution
Important Changes Introduced